Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@CHANGELOG.md`:
- Line 11: Update the changelog entry that currently reads "Converted to class
based resource" to use hyphenated wording "class-based" for correct grammar;
locate the line containing the phrase "Converted to class based resource [Issue
`#151`]" and replace "class based" with "class-based" so the entry reads
"Converted to class-based resource [Issue `#151`]".

In `@source/Classes/020.RDSessionDeployment.ps1`:
- Around line 40-42: The RDSessionDeployment constructor currently doesn't
initialize the $this.ExcludeDscProperties array; update the RDSessionDeployment
() : base ($PSScriptRoot) constructor to set $this.ExcludeDscProperties to an
empty array (or the required default values) so the property is always defined
per coding guidelines—locate the RDSessionDeployment constructor and add
initialization of $this.ExcludeDscProperties there.
- Line 21: The DSC class attribute `[DscResource()]` on the RDSessionDeployment
class is missing the RunAsCredential setting; update the attribute to include a
RunAsCredential value (e.g., change `[DscResource()]` to
`[DscResource(RunAsCredential = 'Optional')]` or `'Mandatory'` as required for
RDSessionDeployment) so the class-based resource declares its run-as credential
policy; locate the `[DscResource]` attribute above the RDSessionDeployment class
and replace it with the appropriate form.
- Around line 5-6: The .DESCRIPTION block for the DSC class resource
RDSessionDeployment is missing the required "## Requirements" and "## Known
issues" subsections; update the comment-based help in the .DESCRIPTION for the
RDSessionDeployment resource to add a "## Requirements" section listing
prerequisites (PowerShell/DSC versions, modules) and a "## Known issues" section
that includes a link to the repository's open issues page on GitHub and any
current caveats; ensure these headings are included in the same .DESCRIPTION
comment block so the DSC class-based resource follows the coding guidelines.

In `@source/en-US/RDSessionDeployment.strings.psd1`:
- Around line 4-6: Remove the literal single-quote characters that were included
in the localized values for RDSessionDeployment_OSRequirementNotMet,
RDSessionDeployment_AddingToDeployment, and
RDSessionDeployment_RemovingFromDeployment so the stored strings are plain
message text (e.g. The minimum OS requirement was not met. (RDSD0001)) and for
messages with placeholders (RDSessionDeployment_AddingToDeployment and
RDSessionDeployment_RemovingFromDeployment) ensure they use the
ConvertFrom-StringData placeholder syntax with {0}, {1} intact and no
surrounding quotes.

In `@source/RemoteDesktopServicesDsc.psd1`:
- Line 33: Replace the wildcard export by setting CmdletsToExport to an empty
array: update the manifest entry for CmdletsToExport (currently "'*'") to @() so
the module does not export any cmdlets; this should match the existing
FunctionsToExport (empty) and the nested module RemoteDesktopServicesDsc.Common
and follow DSC resource module best practices.

In `@tests/Unit/Classes/RDSessionDeployment.Tests.ps1`:
- Around line 303-313: The two test-case hashtables for Property =
'WebAccessServer' (one with Current = $null and the next with Current =
'webaccess.lan') are missing a separating comma; insert a comma after the
closing brace of the first hashtable so the array of hashtables is syntactically
valid (i.e., add a comma between the hashtable ending with Desired =
[System.String[]] @('webaccess1.lan', 'webaccess3.lan') and the following
hashtable).

In `@tests/Unit/Classes/RDSReason.Tests.ps1`:
- Line 59: The Context description string "When setting an reading values"
contains a typo; update the Context declaration in the test (the Context block
whose title is "When setting an reading values") to "When setting and reading
values" so the test description reads correctly.
- Around line 71-74: The test "It 'Should be able read the values from
instance'" mistakenly assigns to $mockRDSReasonInstance.Phrase instead of
asserting its value; replace the assignment ($mockRDSReasonInstance.Phrase =
'...') with an assertion that pipes the property into Should -Be with the
expected string (e.g., $mockRDSReasonInstance.Phrase | Should -Be 'The property
Ensure should be "Present", but was "Absent"') so the test actually verifies the
Phrase property.

---

Nitpick comments:
In `@source/prefix.ps1`:
- Around line 4-9: The two module path variables
($script:dscResourceCommonModulePath and
$script:remoteDesktopServicesDscCommonModulePath) use mixed path separators;
normalize them by using Join-Path consistently for both child paths (e.g.,
replace 'Modules/RemoteDesktopServicesDsc.Common' with
'Modules\RemoteDesktopServicesDsc.Common' or vice versa) so both Import-Module
calls are constructed with the same separator style and readability is
consistent; update the Join-Path childPath argument for the
remoteDesktopServicesDscCommonModulePath to match the pattern used for
dscResourceCommonModulePath.

In `@tests/Unit/Classes/RDSReason.Tests.ps1`:
- Around line 60-68: Add Set-StrictMode -Version 1.0 at the start of the
InModuleScope -ScriptBlock so the test runs with strict mode enabled;
specifically, inside the block that constructs $RDSReasonInstance (the block
using [RDSReason]::new() and assigning .Code and .Phrase), insert the strict
mode call before creating $RDSReasonInstance to ensure undefined variables/typos
are caught during the RDSReasonInstance setup.
- Around line 46-56: The InModuleScope scriptblocks that instantiate the class
must enable strict mode; add a call to Set-StrictMode -Version 1.0 as the first
statement inside each InModuleScope -ScriptBlock before invoking the tested code
(e.g., before [RDSReason]::new() in the block that creates
$script:mockRDSReasonInstance and any other InModuleScope blocks in the
RDSReason tests). Ensure the Set-StrictMode call is placed inside the
scriptblock so it applies to the code under test.

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@source/Classes/020.RDSessionDeployment.ps1`:
- Around line 76-80: The ConnectionBroker return value is taken from
($deployed.Where({ $_.Roles -contains 'RDS-CONNECTION-BROKER' })).Server which
can produce an array if multiple servers match; change the construction to
defensively select a single server (e.g., use Select-Object -First 1 or index
[0] and cast to [System.String]) so ConnectionBroker is always a single string
like WebAccessServer is in Modify(); update the return hash's ConnectionBroker
expression accordingly, referencing the existing deployed variable, Roles,
Server property and the Modify() pattern.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@source/prefix.ps1`:
- Around line 5-9: The Import-Module calls that load the nested modules
($script:dscResourceCommonModulePath and
$script:remoteDesktopServicesDscCommonModulePath) should fail fast on errors;
update the two Import-Module invocations in prefix.ps1 to include the
-ErrorAction Stop parameter so that any import failure throws and prevents
partial/quiet initialization of the module.
- Line 1: The build fails because source/prefix.ps1 contains "using module
.\Modules\DscResource.Base" which requires the DscResource.Base module to exist
at parse-time; fix this by reordering the build pipeline in build.yaml so nested
modules are copied before parsing the main module — specifically ensure the task
sequence runs Build_NestedModules_ModuleBuilder before
Build_Module_ModuleBuilder (e.g., in the build steps run Clean,
Build_NestedModules_ModuleBuilder, Build_Module_ModuleBuilder,
Create_changelog_release_output) so the Modules/DscResource.Base is present when
the module parser runs.

---

Nitpick comments:
In `@source/prefix.ps1`:
- Line 7: Update the TODO comment in source/prefix.ps1 (the line containing
"TODO: The goal would be to remove this, when no classes and public or private
functions need it.") to include a tracker reference (issue ID or milestone) and
short issue link or number (e.g., "#1234" or "issue:repo#1234"); ensure the
comment briefly states the cleanup task and the tracker reference so the TODO is
not orphaned.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@source/Classes/020.RDSessionDeployment.ps1`:
- Around line 76-80: The ConnectionBroker return can be an array when multiple
brokers exist; update the return so ConnectionBroker yields a single
System.String by selecting a single Server from the filtered $deployed (e.g.,
use Select-Object -First 1 or index into the .Where(...) result) and cast it to
[System.String] in the returned hashtable (refer to the ConnectionBroker
property in the return block and the .Where({ $_.Roles -contains
'RDS-CONNECTION-BROKER' }).Server expression).